-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update all non-major dependencies #10833
Conversation
🦋 Changeset detectedLatest commit: 0b3f1ac The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
d5ec377
to
6f9b6ef
Compare
6f9b6ef
to
b7204ac
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
I forgot one annoying thing about renovate, it treats v0 minor updates as non-major, which is technically correct, but is breaking. I handled those below:
|
svelte2tsx update looks fine to me as far as I could tell! We need to watch out with updates to this package because since we depend on the exact shape it generates, even if it says it has no breaking changes, it could still break us. |
@@ -12,6 +12,7 @@ | |||
// manually bumping deps | |||
"@biomejs/biome", | |||
"@types/node", | |||
"preact-render-to-string", // https://github.com/withastro/astro/pull/10200 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
preact-render-to-string
had many updates since, is it still buggy? Maybe it wasn't a bug and I didn't realize, but it definitely did seem like a regression.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it was still buggy. Renovate updated to latest and it returns an array of strings. I'm not sure why though, maybe we're not calling render
right if it's still not fixed.
This PR contains the following updates:
^0.5.8
->^0.5.10
^0.2.3
->^0.4.1
^7.24.3
->^7.24.4
^7.23.3
->^7.24.4
^7.23.3
->^7.24.4
^7.22.5
->^7.23.4
^7.23.3
->^7.24.1
^7.23.3
->^7.24.0
^0.8.0
->^0.10.1
^0.4.8
->^0.5.0
^2.26.2
->^2.27.1
^0.5.5
->^0.6.0
^3.2.0
->^3.2.2
1.1.3
->1.1.7
^1.1.5
->^1.1.7
^1.1.2
->^1.2.0
^0.3.5
->^0.4.0
^3.0.0
->^3.0.1
^6.0.5
->^6.1.0
1.40.0
->1.43.1
^2.7.0
->^2.8.2
^1.2.1
->^1.2.3
^3.0.0
->^3.1.0
^7.20.4
->^7.20.5
^7.6.7
->^7.6.8
^7.20.4
->^7.20.5
^0.5.4
->^0.6.0
^5.0.8
->^5.2.0
^3.0.3
->^3.0.4
^10.0.4
->^10.0.6
^10.0.2
->^10.0.6
^7.2.3
->^7.2.4
^2.4.8
->^2.4.9
^18.2.37
->^18.2.79
^18.2.37
->^18.2.79
^18.2.15
->^18.2.25
^18.2.15
->^18.2.25
^1.20.5
->^1.20.6
^7.5.2
->^7.5.8
^2.4.6
->^2.4.7
^1.0.0
->^1.0.2
^1.0.2
->^1.2.2
^4.2.0
->^4.2.1
^3.3.8
->^3.4.23
^8.11.2
->^8.11.3
^7.12.0
->^7.15.0
^10.4.15
->^10.4.19
^3.5.3
->^3.6.0
^2.0.0
->^2.1.0
^7.0.0
->^7.1.0
^2.0.1
->^2.0.2
^5.1.0
->^5.2.0
^0.30.4
->^0.30.9
^1.4.1
->^1.5.0
^0.19.6
->^0.20.2
^0.19.6
->^0.20.2
^9.0.0
->^9.1.0
^9.0.0
->^9.1.0
^5.0.0
->^5.1.3
^2.2.0
->^2.5.0
^4.18.2
->^4.19.2
^4.2.7
->^4.3.6
^1.1.0
->^1.1.1
1.1.3
->1.2.3
^14.0.0
->^14.0.1
^14.0.0
->^14.0.1
^2.0.0
->^2.0.1
^9.0.0
->^9.0.1
^4.0.0
->^4.0.2
^9.0.0
->^9.1.0